I very much appreciate your PR. But the sample config should not be used in production. I don't think we should put effort into making sure that the listed logs are all up and replying. At some point the Nessie2022 log will also probably not be replying to requests.

The sample config should just be, well, an example for all the possible configuration options.

If there are more reasons to why we should remove it, please let me know. Currently I am kind of hesitant because I don't want to update the sample config each year.

The Docker imagine will use the sample config if no configuration is provided. Additionally, I want to add an example of a tiled log and I think that one standard log in the sample config is more than enough.

I think that there is no harm in removing that log from the sample config. We could always think about a more appropriate long term solution afterwards.

I also think that users will just copy the sample config and apply only the minimum required changes to get the server working. They won't think much about the CT logs listed there.

I am not a big fan of keeping the sample config up to date. As a short term solution this is fine, but for long term we should think about better solutions. We were already at that point in the past. See

#65 (comment) and #67 for more context.